| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.1.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_1_1_Manage_Provider_Registry_or_Directory |
| Title | AS.1.1 Manage Provider Registry or Directory (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide a current registry or directory of practitioners that contains data needed to determine levels of access required by the system. |
| Purpose | Provider information may include any credentials, certifications, or any other information that may be used to verify that a practitioner is permitted to use or access authorized data. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide a current registry or directory of practitioners that contains data needed to determine levels of access required by the system.
Provider information may include any credentials, certifications, or any other information that may be used to verify that a practitioner is permitted to use or access authorized data.
| AS.1.1#01 | dependent SHOULD |
The system SHOULD provide the ability to manage a registry or directory of all personnel who currently use or access the system according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.1.1#02 | SHOULD |
The system SHOULD provide the ability to capture and maintain realm-specific legal identifiers required for care delivery (e.g., the provider's license number or national provider identifier). |
| AS.1.1#03 | SHALL |
The system SHALL provide the ability to capture and maintain the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant). |
| AS.1.1#04 | SHOULD |
The system SHOULD link provider information in the registry or directory with the security function to determine or identify authorized levels of access. |
| AS.1.1#05 | MAY |
The system MAY provide the ability to manage a directory of clinical/support personnel external to the organization that are not users of the system (to facilitate documentation and information communication). |
| AS.1.1#06 | dependent SHOULD |
The system SHOULD provide the ability to update the provider's access to the requested patient's information when a patient-provider relationship is established in the system (e.g., when patient is cared for in Emergency, system enables emergency attending provider to access patient's information); according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.1.1#07 | conditional SHALL |
IF [[TI.3]] (Registry and Directory Services) is implemented, THEN the system SHALL conform to function [[TI.3]] and provide the ability to use registries or directories to uniquely identify providers for the provision of care. |
| AS.1.1#08 | SHOULD |
The system SHOULD provide the ability for authorized users to hide selected elements of the registry or directory information for the users of the system based on the user's security level and access needs. For example, the administrator hides from data-entry clerks the name of the data-entry clerk's immediate relatives who are listed on the hospital's cancer registry. |
| AS.1.1#09 | MAY |
The system MAY provide the ability to maintain a registry or directory which identifies the provider by multiple unique identifiers. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.1.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide a current registry or directory of practitioners that contains data needed to determine levels of access required by the system.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Provider information may include any credentials, certifications, or any other information that may be used to verify that a practitioner is permitted to use or access authorized data.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage a registry or directory of all personnel who currently use or access the system according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain realm-specific legal identifiers required for care delivery (e.g., the provider's license number or national provider identifier).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and maintain the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD link provider information in the registry or directory with the security function to determine or identify authorized levels of access.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage a directory of clinical/support personnel external to the organization that are not users of the system (to facilitate documentation and information communication).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update the provider's access to the requested patient's information when a patient-provider relationship is established in the system (e.g., when patient is cared for in Emergency, system enables emergency attending provider to access patient's information); according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF [[TI.3]] (Registry and Directory Services) is implemented, THEN the system SHALL conform to function [[TI.3]] and provide the ability to use registries or directories to uniquely identify providers for the provision of care.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for authorized users to hide selected elements of the registry or directory information for the users of the system based on the user's security level and access needs. For example, the administrator hides from data-entry clerks the name of the data-entry clerk's immediate relatives who are listed on the hospital's cancer registry.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.1#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to maintain a registry or directory which identifies the provider by multiple unique identifiers.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.1",
"version" : "2.1.0",
"name" : "AS_1_1_Manage_Provider_Registry_or_Directory",
"title" : "AS.1.1 Manage Provider Registry or Directory (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide a current registry or directory of practitioners that contains data needed to determine levels of access required by the system.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Provider information may include any credentials, certifications, or any other information that may be used to verify that a practitioner is permitted to use or access authorized data.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.1.1-01",
"label" : "AS.1.1#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage a registry or directory of all personnel who currently use or access the system according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.1#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-02",
"label" : "AS.1.1#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain realm-specific legal identifiers required for care delivery (e.g., the provider's license number or national provider identifier).",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.1#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-03",
"label" : "AS.1.1#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and maintain the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-04",
"label" : "AS.1.1#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD link provider information in the registry or directory with the security function to determine or identify authorized levels of access.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.1#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-05",
"label" : "AS.1.1#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage a directory of clinical/support personnel external to the organization that are not users of the system (to facilitate documentation and information communication).",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.1#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.1.1-06",
"label" : "AS.1.1#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update the provider's access to the requested patient's information when a patient-provider relationship is established in the system (e.g., when patient is cared for in Emergency, system enables emergency attending provider to access patient's information); according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-07",
"label" : "AS.1.1#07",
"conformance" : [
"SHALL"
],
"conditionality" : true,
"requirement" : "IF [[TI.3]] (Registry and Directory Services) is implemented, THEN the system SHALL conform to function [[TI.3]] and provide the ability to use registries or directories to uniquely identify providers for the provision of care.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.7#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-08",
"label" : "AS.1.1#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for authorized users to hide selected elements of the registry or directory information for the users of the system based on the user's security level and access needs. For example, the administrator hides from data-entry clerks the name of the data-entry clerk's immediate relatives who are listed on the hospital's cancer registry.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.3.7#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.1-09",
"label" : "AS.1.1#09",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to maintain a registry or directory which identifies the provider by multiple unique identifiers."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.